fix #1213

Summary

The client environment's optimizeDeps.include only listed
react-dom/client and one React Server DOM entry — not react,
react/jsx-runtime, or any of the React-peer packages crawled by
crawlFrameworkPkgs. Those got discovered lazily as the browser
requested modules, the optimizer re-ran mid-load, and the ?v= hash
changed on chunks that had already been served. The browser ended up
with two distinct React module records, and 'use client' libraries
that synchronously call hooks in providers hit the wrong dispatcher
(React.H is null), throwing Invalid hook call.

The ssr and rsc envs don't hit this because their
optimizeDeps.include already lists react, react-dom,
react/jsx-runtime, and react/jsx-dev-runtime.

Change

Mirror the SSR/RSC env behaviour for the client env: pre-include
those four React subpaths plus the React-peer packages that
crawlFrameworkPkgs already discovers for noExternal. Filter that
spread to packages whose bare specifier resolves from the user's
project root — server-only React peers (e.g. the
@vitejs/test-dep-client-in-server test fixture, which only exports
./server) would otherwise break dep optimization.

Reproduction

Repro repo: https://github.com/jgeurts/vite-rsc-cjs-subpath-named-exports

git clone https://github.com/jgeurts/vite-rsc-cjs-subpath-named-exports
cd vite-rsc-cjs-subpath-named-exports
npm install
rm -rf node_modules/.vite
npm run dev
# open http://localhost:5173/

The page mounts, then the browser console shows two Invalid hook call
errors and a TypeError: Cannot read properties of null (reading 'useMemo')
where the React, @liveblocks_react, and react-dom_client chunks each
carry a different ?v= hash. With this PR applied (drop the patched
@vitejs/plugin-rsc into the repro's node_modules), the page renders
cleanly.

Verification

• All 424 plugin-rsc unit tests pass (pnpm test).
• examples/basic runs cleanly in pnpm dev and pnpm build after
  the change. The fixture exercises a wide range of 'use client' /
  'use server' paths, including the @vitejs/test-dep-client-in-server
  fixture that lacks a . export — confirms the resolution-based filter
  works.
• New regression test e2e/use-client-hook-in-provider.test.ts stands
  up an isolated dev fixture with a 'use client' package that calls
  useMemo synchronously in a Provider. With the fix it passes; with
  the fix reverted it fails the dev case (the build case still passes —
  this bug is dev-only).
• Repro repo (linked above) loads cleanly with the patched plugin.